<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
       "http://www.w3.org/TR/html4/loose.dtd">
<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>ECF New and Noteworthy</title>
<link rel="stylesheet" href="http://www.eclipse.org/default_style.css"
	type="text/css">

</head>

<body bgcolor="#FFFFFF">
	<table border=0 cellspacing=5 cellpadding=2 width="100%">
		<tbody>
			<tr>
				<td width="69%" class="bannertext">
				<img src="https://wiki.eclipse.org/images/b/b8/Logo128x37.png" alt="ECF Logo"/>
				<font class="indextop style">eclipse
						communication framework</font> <br>
				<br> <font class="indexsub">an eclipse runtime project</font> <br>
				<br> <font class="indextop style2">New and Noteworthy</font><br>
					3.6.1 Release <br> <br>
				<br> Return to <a href="downloads.php">ECF download page</a><br>
					<br>
				<br> <a href="NewAndNoteworthy_3.5.2.html">New and
						Noteworthy for 3.5.2</a><br> <a
					href="NewAndNoteworthy_3.5.0.html">New and Noteworthy for 3.5.1</a><br>
					<a href="NewAndNoteworthy_3.5.0.html">New and Noteworthy for
						3.5.0</a><br>
					<br>
				<br></td>
				<td width="31%">
					<div align="center">
						<img src="images/Idea.jpg" width="120" height="86" hspace="50"
							align="middle" alt="Idea Icon">
					</div>
				</td>
			</tr>
		</tbody>
	</table>

	<hr>

	<table>
		<tr>
			<td valign="top" align="left" width="15%">
				<p align="left">
					<b>Remote Service Admin Passes OSGi R5 Compatibility Tests</b>
				</p>
			</td>
			<td valign="top" width="85%">
				<p>Since OSGi version 4.2, ECF has provided an implementation of the <a href="http://wiki.eclipse.org/ECF#OSGi_Remote_Services">OSGi Remote Services specification</a>, and
				the <a href="http://wiki.eclipse.org/Remote_Services_Admin">Remote Services Admin (RSA) specification</a>.  For <a href="http://www.osgi.org/Release5/HomePage">OSGi R5</a>, 
				the ECF team has tested the implementation against the OSGi Test Compatibility Kit (TCK), which is
				a set of tests that assure compatibility of the implementation with the RS/RSA specifications.  
After fixing some compatibility problems (see <a href="https://bugs.eclipse.org/bugs/buglist.cgi?list_id=5944292&short_desc=%5BTCK%5D&classification=RT&query_format=advanced&short_desc_type=allwordssubstr&product=ECF">tck bugs here</a>),
				we are now passing all the TCK tests, and are verifiably compatible with the R5 RS/RSA specifications.  </p><br>
			</td>
		</tr>
		<tr>
			<td valign="top" align="left" width="15%">
				<p align="left">
					<b><a
						href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=391677">Generic provider using TLS/SSL transport</a></b>
				</p>
			</td>
			<td valign="top" width="85%">
				<p>
					Earlier ECF general providers were based on raw TCP sockets. Thus
					encrypted communication through the ECF generic provider for OSGI Remote Service
					was not available.  A new 
					provider was developed to support secure/encrypted communication
					based upon SSL.  See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=391677">bug 391677</a><br>
			</td>
		</tr>
		<tr>
			<td valign="top" align="left" width="15%">
				<p align="left">
					<b><a
						href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=337615">Server-side REST Remote Services</a></b>
				</p>
			</td>
			<td valign="top" width="85%">

				<p>
					In previous versions of ECF, Rest API mostly supported the creation of
					OSGI Remote Service clients/consumers.  This work on supports the creation and
					use of remote services on OSGi-based servers. Major additions can be
					found in org.eclipse.ecf.remoteservice.server bundle. Also some
					changes were made to the <a
						href="https://github.com/ECF/RestletProvider">Restlet provider</a> (available via <a href="http://github.com/ECF">ECF Github Repo</a>).

				</p> <br>
			</td>
		</tr>
		<tr>
			<td valign="top" align="left" width="15%">
				<p align="left">
					<b><a
						href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=256975">Remote Service Tracker</a></b>
				</p>
			</td>
			<td valign="top" width="85%">
				<p> ServiceTrackers are used to discover registered services
					and then consume them.   This RemoteServiceTracker allows the
					tracking of ECF RemoteService instances, which does not need
					the OSGi service registry to function (as normal service trackers do).
                </p>
    <br>
			</td> 
  </tr> 
    <tr> 
    <td valign="top" align="left" width="15%"> 
        <p align="left"> 
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=400164">Remote Services Proxy creation API</a></b> 
        </p> 
    </td> 
    <td valign="top" width="85%"> 
    
    <p>Earlier remote services proxy creation is done by using<br>
    AbstractRemoteService.createProxy/2<br>
    In order to customize the proxy creation it was necessary to subclass AbstractRemoteService and override createProxy. But with new contributions
    proxy creation can be dynamically customized using IRemoteServiceProxyCreator with an appropriate service ranking.    
    </p>
	<br>
    </td> 
  </tr> 
    <tr> 
    <td valign="top" align="left" width="15%"> 
        <p align="left"> 
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=337449">Filetransfer provider using Apache HttpClient 4.1</a></b> 
        </p> 
    </td> 
    <td valign="top" width="85%"> 
    
    <p>Active work on Apache HttpClient version 3.X has stopped, and Apache HttpComponents/HttpClient4 is now where active dev and bug fixing work is taking place. 
    ECF has created and deployed a new provider based upon HttpClient 4, that will allow p2/Equinox/Eclipse platform to benefit from the new Apache HttpClient 4 work,
    including such desired features as full support for NTLM proxies, HTTP caching, improved proxy and credentials support, and active debugging.
	</p>
	<br>
	<br>
    </td> 
  </tr>  
    <tr> 
    <td valign="top" align="left" width="15%"> 
        <p align="left"> 
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=408034">IRemoteCallParameterSerializer.serializeParameter can only serialize to a single parameter</a></b> 
        </p> 
    </td> 
    <td valign="top" width="85%"> 
    
    <p>Incompatibilities between ECF 3.6.0 and 3.6.1:<br>

ECF changed in an incompatible way between 3.6.0 and 3.6.1 in ways that affect 
consumers of ECF remote services. The following entry describes the area that changed and provides 
instructions for migrating from 3.6.0 to 3.6.1.
<br>
What is affected: Consumers that provide an implementation for o.e.e.remoteservice.client.IRemoteCallParameterSerializer.
<br>
Description: ECF 3.6.1 has added a second method to the interface. This change brings improved support for advanced serialization of call parameters. 
However, this change also is an incompatible change for pre 3.6.1 implementers of the interface.
<br>
Action required: Consumers that directly implement IRemoteCallParameterSerializer have to choose a migration path. Either provide a method implementation for the newly introduced interface method, or inherit from o.e.e.remoteservice.client.AbstractParameterSerializer. AbstractParameterSerializer provides a default implementation for the new interface method behavior compatible to ECF 3.6.0. Number two is generally preferred.
	</p>
	<br>
	<br>
    </td> 
  </tr>  
		<tr>
			<td valign="top" align="left" width="15%">
				<p align="left">
					<b>Updated Restlet Provider</b>
				</p>
			</td>
			<td valign="top" width="85%">
				<p>ECF has updated it's Restlet Remote Services Provider (to Restlet 2.2) available on Github <a href="https://github.com/ECF/RestletProvider">here</a></p><br>
			</td>
		</tr>
		<tr>
			<td valign="top" align="left" width="15%">
				<p align="left">
					<b>Updated JMS Provider</b>
				</p>
			</td>
			<td valign="top" width="85%">
				<p>ECF has <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=410237">updated</a> it's JMS/ActiveMQ Provider (to ActiveMQ 5.8.0) available on Github <a href="https://github.com/ECF/JMS">here</a></p><br>
			</td>
		</tr>
</table> 
 
</body> 
</html> 
